Click any tag below to further narrow down your results
Links
A roundup of recent Anthropic updates covering customizable Claude Code mods, a cheaper Opus 5.5 model with higher session limits, a new open-source commerce agent blueprint, and the stateless MCP protocol release.
- Claude Code now supports mods shipped as plugins, letting you change behavior, customize the UI, or add features, installed via /plugin.
- Opus 5.5 is about 30% faster and 40% cheaper per task than Opus 5, and is the default for paid plans, with 5-hour session limits up 20%.
- MCP 2026-07-28 makes the protocol stateless, so remote servers can run on serverless or edge infrastructure and scale behind any load balancer.
A roundup of recent Anthropic posts on Twitter/X covering customizable Claude Code mods, the Opus 5.5 model with usage limit boosts, and the 2026-07-28 MCP spec release that makes the protocol stateless. The thread itself is a collection of tweets, so this is a digest rather than a single argument.
- Claude Code can now be modded through plugins, with examples like Token Weather (context window forecast) and Blast Radius (flags risky shell commands before they run).
- Opus 5.5 is reported as roughly 30% faster and 40% cheaper per task than Opus 5, becoming the default for paid plans, with 5-hour session limits raised 20% and a one-time usage reset available until Oct 22.
- MCP 2026-07-28 makes the protocol stateless, so remote servers can run on serverless or edge infrastructure and scale horizontally, and adds formal extensions like MCP Apps, Tasks, and Enterprise Managed Auth.
@vartekxx on X
This is a how-to guide for connecting Anthropic's Opus 5.5 model to a Dots (ChatGPT-based) team as an external tool, so the orchestrating dot can hand off deep research, stricter reviews, chart reading, and long-running batch work. The author argues Dots stays fast but skims complex sources, uses flat effort, and reviews weakly.
- The bridge is a single private tool, run_opus_task, built with the Apps SDK or MCP, with the Anthropic key kept on a backend the user controls and read-only access to start.
- Reviews should come from a separate run that does not produce the work, with a strict JSON schema (additionalProperties: false) so every failure needs evidence and unverifiable claims must be declared.
- Cost savings come from prompt caching: put the unchanging material first, add a breakpoint, and rely on the one-hour TTL so a team's morning, midday, and lunchtime runs share one cache write.